Systems and methods for communication network customization

ABSTRACT

Systems and methods are provided for identifying an available infrastructure network topology consisting of a set of available network links and a set of available network nodes of a communication network. In the systems and methods, a network node of the communication network is operative to transmit a learning schedule to a plurality of network nodes interconnected by a set of network links of the communication network. The network node receives from each of the plurality of network nodes a communication node record including network performance observations observed by that network node based on the learning schedule transmitted to that network node. Based on the received communication node records, the network node identifies a set of available network links from the set of network links and the set of available network nodes corresponding to the set of available network links.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority of U.S. Provisional Patent ApplicationSer. No. 62/833,365, entitled “Systems and Methods for CommunicationNetwork Customization” filed Apr. 12, 2019, the contents of which areincorporated herein by reference.

FIELD OF THE INVENTION

The present invention generally pertains to the field of communicationnetworks, and particular embodiments or aspects relate to customizationof communication networks to meet service requirements.

BACKGROUND

Next generation communication networks are proposed to have a flexiblearchitecture based on the virtualization of network functions that maybe distributed and dynamically modified across the network hardwareinfrastructure. The concept of a network slice, a logical virtualnetwork instantiated over a next generation network, allows for flexibleprovision of service and charging levels for individual customers orelectronic devices accessing the network slice.

Vertical/industry customers will likely become separate customerentities for future communication networks, as opposed to the end usermodel currently employed by wireless network providers. Thesevertical/industry customers may include, for instance, factories, farms,smart cities, mobile hospitals, utility providers, mobile and stationaryservice providers, etc. The main characteristics of such customers mayinclude some or all of the following attributes: common ownership forthe connectivity of multiple electronic devices; common responsibilityfor the connectivity of multiple electronic devices; known service levelcommunication requirements and network topologies; predictable trafficpatterns; predictable mobile paths; desire and capability to deployprivate infrastructure network(s) with or without the support of networkoperators/vendors/etc.

As an example, a utility service provider may provide each of itscustomers with a smart meter deployed at their home or business to trackutility consumption, provide utility service metrics, or both. The smartmeters may comprise electronic devices that include communicationfunctionality to connect to a communication network (wired orwirelessly) to automatically feed back utility information to theutility provider that may include utility consumption metrics, utilityservice metrics, or both. In some cases, the utility service providermay further include mobile electronic devices that exchange utilityinformation with utility provider fixed infrastructure. It would beuseful for the utility service provider to have a virtual networkestablished on an operator's network that flexibly, efficiently, andeconomically supports the communication needs of the utility provider.

In general, there is a need for a communication network customizationthat provides for a network that may be automatically deployed,automatically operated, automatically maintained, or a combinationthereof.

Accordingly, there may be a need for systems and methods forcustomization of communication networks to meet service requirementsthat is not subject to one or more limitations of the prior art.

This background information is intended to provide information that maybe of possible relevance to the present invention. No admission isnecessarily intended, nor should be construed, that any of the precedinginformation constitutes prior art against the present invention.

SUMMARY

In embodiments, systems and methods are provided for customizing avirtual network that include learning available infrastructure networktopology and determining an available infrastructure network, anddesigning one or more service-based slice/virtual networks for eachtypes of service to be supported. The embodiments may include, forinstance, designing and configuring the infrastructure network topologyand Transmission (Tx)/Receiving (Rx) scheduling requirements of eachcommunication party requiring access to the service (network nodes,electronic devices (fixed and/or mobile) onto the infrastructure networknodes and electronic devices. In some embodiments, the customizing maybe performed once and then the virtual network is operated as a fixedcustomized network. In some embodiments, the customizing may beperformed dynamically and then the virtual network is operated as adynamically customized network that allocates and modifies resourcesduring operation to match network performance to current servicerequirements for that virtual network. The systems and methods providefor a solution that increase flexibility of on-demand deployment of avirtual network on an existing infrastructure network to supportchanging customer requirements, or predictably varying customerrequirements.

In an embodiment a method is provided for identifying an availableinfrastructure network topology consisting of a set of available networklinks and a set of available network nodes of a communication network.The method may be performed by a network node (e.g. an infrastructurenetwork learning controller) of the communication network. The methodincludes transmitting a learning schedule to a plurality of networknodes interconnected by a set of network links of the communicationnetwork. The method includes receiving from each of the plurality ofnetwork nodes a communication node record including network performanceobservations observed by that network node based on the learningschedule transmitted to that network node. The method includesidentifying (e.g. providing an identification of) a set of availablenetwork links from the set of network links based on the receivedcommunication node records, and identifying the set of available networknodes corresponding to the set of available network links. The learningschedule may direct the plurality of network nodes to perform specifiedcommunication operations and record network performance operations basedon the communication operations.

In some aspects, the learning schedule further includes an updateschedule for each of the plurality of network nodes to transmitcommunication node records to the communication node, and the method mayfurther include receiving, from each of the plurality of network nodes,the communication record for that network node according to thecorresponding update schedule.

In some aspects, the method may further include the network node oranother network node, such as a slice customization controller:determining a customized network slice topology based on a service leveltopology and the available infrastructure network topology. The servicelevel topology may be defined by a customer. The service level topologymay define a subset of the plurality of network nodes and communicationrequirements therebetween, the customized network slice topologyspecifying network nodes and interconnections from the availableinfrastructure network topology which are adequate for delivering aservice according to the service level topology.

In some aspects, the method may further include the network node oranother network node, such as an infrastructure network customizationmanager: configuring the set of available network nodes based on thedetermined customized network slice topology. The configuring may beperformed prior to deployment of the service and is typically restrictedto configuring a subset of the nodes. The configuring may includedirecting the subset of the nodes to communicate according to a fixedresource allocation, which includes a fixed communication schedule whichis communicated to the nodes and thereafter used by the nodes, typicallyfor multiple communications.

Additionally, the network node may include one or more means or unitsfor carrying out the steps of the methods in the embodiments of thispresent invention. For example, the steps include receiving from each ofthe plurality of network nodes at least one further communication noderecord including network performance observations observed by thatnetwork node after the set of available network nodes has beenconfigured; and, evaluating the set of network links based on the atleast one further communication record. In some aspects, the at leastone further communication node record is received based the learningschedule. In some aspects, the at least one further communication noderecord is received based on a request previously transmitted by thenetwork node to the set of network nodes. In some aspects, the networknode may further carry out the step of: changing at least one of the setof available network links or the determined network slice topologybased on the at least one further communication record.

In some embodiments, a network function or device, such as aninfrastructure network learning controller (operative for example on anetwork node) is provided. The network function or device includes anetwork interface for receiving data from and transmitting data tonetwork functions connected to a communication network; a processor; anda non-transient memory for storing instructions. The instructions, whenexecuted by the processor, cause the network function to be configuredto identify an available infrastructure network topology consisting of aset of available network links and a set of available network nodes ofthe communication network. The network function or device is operativeto: transmit a learning schedule to a plurality of network nodesinterconnected by a set of network links of the communication network;receive from each of the plurality of network nodes a communication noderecord including network performance observations observed by thatnetwork node based on the learning schedule transmitted to that networknode; and identify a set of available network links from the set ofnetwork links based on the received communication node records, andidentifying the set of available network nodes corresponding to the setof available network links. The learning schedule may direct theplurality of network nodes to perform specified communication operationsand record network performance observations based on said communicationoperations.

In some aspects, the learning schedule further includes an updateschedule for each of the plurality of network nodes to transmitcommunication node records to the communication node, and wherein thenetwork node is further operative to: receive, from each of theplurality of network nodes, the communication record for that networknode according to the corresponding update schedule.

In some aspects, the network function or device, or another associatednetwork function or device such as a slice customization controller, isfurther operative to: determine a customized network slice topologybased on a service level topology and the available infrastructurenetwork topology.

In some aspects, the network function or device, or another associatednetwork function or device such as an infrastructure networkcustomization manager, is further operative to: configure the set ofavailable network nodes based on the determined network slice topology.In some aspects, the network function is further operative to: receivefrom each of the plurality of network nodes at least one furthercommunication node record including network performance observationsobserved by that network node after the set of available network nodeshas been configured; and, evaluate the set of network links based on theat least one further communication record. The at least one furthercommunication node record may be received based on a request previouslytransmitted by the network node to the set of network nodes. The atleast one further communication node record may be received based on thelearning schedule.

In some aspects, the network function may further be operative to changeat least one of the set of available network links or the determinednetwork slice topology based on the at least one further communicationrecord.

In some aspects, the set of available network links is identified byevaluating (e.g. by the network function) communication node recordscorresponding to each network link based on a pre-determined performancerequirement set for that network link.

In some aspects, pre-determined performance requirement comprises asignal-to-noise ratio (SNR) threshold for that network link.

According to an embodiment, there is provided a method for defining acustomized network slice topology to be established using a plurality ofnetwork nodes interconnected by a set of network links of acommunication network. The method may be performed by a slicecustomization controller of the communication network, or associatednetwork function. The method includes receiving a customer-definedservice level topology defining a subset of the plurality of networknodes and communication requirements therebetween. The method includesreceiving an indication of an available infrastructure network topologyconsisting of a set of available network nodes and a set of availablenetwork links interconnecting the set of available network nodes, theavailable infrastructure network topology identified based onobservations, by the plurality of network nodes, of network operationsin comparison with specified network performance criteria. The methodincludes transmitting an indication of the customized network slicetopology determined based on the customer-defined service level topologyand the available infrastructure network topology, the customizednetwork slice topology specifying network nodes and interconnectionsfrom the available infrastructure network topology which are adequatefor delivering a service according to the service level topology.

According to an embodiment, there is provided a method for configuring acommunication network to deliver a service. The communication networkincludes a plurality of network nodes interconnected by a set of networklinks of the communication network. The method may be performed by aninfrastructure network customization manager of the communicationnetwork, or associated network function. The method includes receivingan indication of an available infrastructure network topology consistingof a set of available network nodes and a set of available network linksinterconnecting the set of available network nodes, the availableinfrastructure network topology identified based on observations, by theplurality of network nodes, of network operations in comparison withspecified network performance criteria. The method includes receiving acustomized network slice topology specifying network nodes andinterconnections from the available infrastructure network topologywhich are adequate for delivering the service. The method includes,prior to deployment of the service, transmitting instructions to asubset of nodes belonging to the set of available network nodes, theinstructions configuring said subset of nodes to communicate accordingto a fixed resource allocation including a fixed communication schedule.The subset of nodes and the fixed resource allocation are set so thatthey are adequate to deliver the service according to the customizednetwork slice topology.

According to an embodiment, there is provided an infrastructure networklearning controller comprising: a network interface for receiving datafrom and transmitting data to network functions connected to acommunication network; a processor; and a non-transient memory forstoring instructions. The instructions, when executed by the processor,cause the infrastructure network learning controller to be configured toidentify an available infrastructure network topology consisting of aset of available network links and a set of available network nodes ofthe communication network. The infrastructure network learningcontroller is operative to transmit a learning schedule to a pluralityof network nodes interconnected by a set of network links of thecommunication network, the learning schedule directing the plurality ofnetwork nodes to perform specified communication operations and recordnetwork performance observations based on said communication operations.The controller is further operative to receive, from each node of theplurality of network nodes, a respective communication node recordincluding the network performance observations observed by said nodebased on the learning schedule transmitted to said node. The controlleris further operative to provide an identification of the set ofavailable network links from the set of network links based on thereceived communication node records. The controller is further operativeto provide an identification of the set of available network nodescorresponding to the set of available network links.

According to an embodiment, there is provided a slice customizationcontroller comprising: a network interface for receiving data from andtransmitting data to network functions connected to a communicationnetwork; a processor; and a non-transient memory for storinginstructions. The instructions, when executed by the processor, causethe slice customization controller to be configured to define acustomized network slice topology to be established using a plurality ofnetwork nodes interconnected by a set of network links of acommunication network. The slice customization controller is operativeto receive a customer-defined service level topology defining a subsetof the plurality of network nodes and communication requirementstherebetween. The controller is further operative to receive anindication of an available infrastructure network topology. The topologyincludes a set of available network nodes and a set of available networklinks interconnecting the set of available network nodes. The availableinfrastructure network topology is identified based on observations, bythe plurality of network nodes, of network operations in comparison withspecified network performance criteria. The controller is furtheroperative to transmit an indication of the customized network slicetopology determined based on the customer-defined service level topologyand the available infrastructure network topology, the customizednetwork slice topology specifying network nodes and interconnectionsfrom the available infrastructure network topology which are adequatefor delivering a service according to the service level topology.

According to an embodiment, there is provided an infrastructurecustomization manager comprising: a network interface for receiving datafrom and transmitting data to network functions connected to acommunication network; a processor; and a non-transient memory forstoring instructions. The instructions, when executed by the processor,cause the infrastructure customization manager to be configured toconfigure a communication network to deliver a service. Thecommunication network includes a plurality of network nodesinterconnected by a set of network links of the communication network.The infrastructure customization manager is operative to: receive anindication of an available infrastructure network topology consisting ofa set of available network nodes and a set of available network linksinterconnecting the set of available network nodes. The availableinfrastructure network topology is identified based on observations, bythe plurality of network nodes, of network operations in comparison withspecified network performance criteria. The manager is operative toreceive a customized network slice topology specifying network nodes andinterconnections from the available infrastructure network topologywhich are adequate for delivering the service. The manager is operative,prior to deployment of the service, to transmit instructions to a subsetof nodes belonging to the set of available network nodes. Theinstructions configure the subset of nodes to communicate according to afixed resource allocation including a fixed communication schedule. Thesubset of nodes and the fixed resource allocation are adequate todeliver the service according to the customized network slice topology.

It is noted that, in some embodiments, multiple network nodes, functionsor devices may operate together in a system which is provided accordingto embodiments of the present invention. For example, a system may beprovided which includes two or more of: an infrastructure networklearning controller, a slice customization function, and aninfrastructure network customization manager.

Embodiments have been described above in conjunctions with aspects ofthe present invention upon which they can be implemented. Those skilledin the art will appreciate that embodiments may be implemented inconjunction with the aspect with which they are described, but may alsobe implemented with other embodiments of that aspect. When embodimentsare mutually exclusive, or are otherwise incompatible with each other,it will be apparent to those skilled in the art. Some embodiments may bedescribed in relation to one aspect, but may also be applicable to otheraspects, as will be apparent to those of skill in the art.

BRIEF DESCRIPTION OF THE FIGURES

Further features and advantages of the present invention will becomeapparent from the following detailed description, taken in combinationwith the appended drawings, in which:

FIG. 1 is a block diagram of an electronic device 52 within a computingand communications environment 50 that may be used for implementingdevices and methods in accordance with representative embodiments of thepresent invention;

FIG. 2, is a flow chart illustrating an embodiment of a method forcustomizing a communication network;

FIG. 3 illustrates an available infrastructure network topology learningschedule and an observation reporting schedule, for customizing acommunication network according to embodiments of the present invention;

FIG. 4 illustrates a method for reporting a communication node recordindicative of the available communication elements contactable by thatnetwork node, according to embodiments of the present invention;

FIG. 5 illustrates a method for learning an available infrastructurenetwork topology based on pre-configured acceptable signal-to-noiseratio (SNR) criteria and the received communication node records foreach reporting node, according to embodiments of the present invention;

FIG. 6A illustrates a use case example embodiment of the presentinvention, assuming fixed nodes/devices and deterministic traffic;

FIG. 6B illustrates another use case example embodiment of the presentinvention;

FIG. 7 illustrates a use case example embodiment of the presentinvention, assuming a combination of fixed nodes/devices and mobiledevices having non-predictable mobile paths and traffic pattern;

FIG. 8 illustrates a use case example embodiment of the presentinvention, assuming fixed nodes/devices and a predictable trafficpattern;

FIG. 9 illustrates determination of a customized network slice orslices, based on an available infrastructure network topology and aservice level topology defined for the service to be supported,according to embodiments of the present invention;

FIG. 10 illustrates determination of a customized infrastructure networkbased on an available infrastructure network topology and a designedservice-customized slice, according to embodiments of the presentinvention;

FIG. 11 illustrates learning for a combined fixed and mobile layout,according to embodiments of the present invention;

FIG. 12 illustrates an example use case in which a service-customizednetwork slice is defined, according to embodiments of the presentinvention; and,

FIG. 13 illustrates an example use case in which a customizedinfrastructure network is allocated and configured based on aservice-customized network slice and the available infrastructurenetwork topology, according to embodiments of the present invention.

DETAILED DESCRIPTION

In embodiments, the systems and methods provide for a solution thattakes advantage of characteristics of predictability in communicationnetwork use and requirements to simplify operation of a network. Inembodiments, the systems and methods provide for a solution that takesadvantage of flexibility of on-demand deployment of a virtual network onan existing infrastructure network to support changing customerrequirements, or predictably varying customer requirements. Inembodiments, the systems and methods provide for a solution thatintegrates conventional control and management planes functions of avirtual network to simplify the operation and management of the virtualnetwork.

FIG. 1 is a block diagram of an electronic device (ED) 52 illustratedwithin a computing and communications environment 50 that may be usedfor implementing the devices and methods disclosed herein. Theelectronic device can be configured by programming same to implementvarious functions and operations as discussed herein. In someembodiments, the electronic device may be an element of communicationsnetwork infrastructure, such as a base station (for example a NodeB, anenhanced Node B (eNodeB), a next generation NodeB (sometimes referred toas a gNodeB or gNB), a home subscriber server (HSS), a gateway (GW) suchas a packet gateway (PGW) or a serving gateway (SGW) or various othernodes or functions within an evolved packet core (EPC) network. In otherembodiments, the electronic device may be a device that connects tonetwork infrastructure over a radio interface, such as a mobile phone,smart phone or other such device that may be classified as a UserEquipment (UE). In some embodiments, ED 52 may be a Machine TypeCommunications (MTC) device (also referred to as a machine-to-machine(m2m) device), or another such device that may be categorized as a UEdespite not providing a direct service to a user. In some references, anED may also be referred to as a mobile device, a term intended toreflect devices that connect to mobile network, regardless of whetherthe device itself is designed for, or capable of, mobility. Specificdevices may utilize all of the components shown or only a subset of thecomponents, and levels of integration may vary from device to device.Furthermore, a device may contain multiple instances of a component,such as multiple processors, memories, transmitters, receivers, etc. Theelectronic device 52 typically includes a processor 54, such as aCentral Processing Unit (CPU), and may further include specializedprocessors such as a Graphics Processing Unit (GPU) or other suchprocessor, a memory 56, a network interface 58 and a bus 60 to connectthe components of ED 52. ED 52 may optionally also include componentssuch as a mass storage device 62, a video adapter 64, and an I/Ointerface 68 (shown in dashed lines).

The memory 56 may comprise any type of non-transitory system memory,readable by the processor 54, such as static random access memory(SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM),read-only memory (ROM), or a combination thereof. In an embodiment, thememory 56 may include more than one type of memory, such as ROM for useat boot-up, and DRAM for program and data storage for use whileexecuting programs. The bus 60 may be one or more of any type of severalbus architectures including a memory bus or memory controller, aperipheral bus, or a video bus.

The electronic device 52 may also include one or more network interfaces58, which may include at least one of a wired network interface and awireless network interface. As illustrated in FIG. 1, network interface58 may include a wired network interface to connect to a network 74, andalso may include a radio access network interface 72 for connecting toother devices over a radio link. When ED 52 is network infrastructure,the radio access network interface 72 may be omitted for nodes orfunctions acting as elements of the Core Network (CN) other than thoseat the radio edge (e.g. an eNB). When ED 52 is infrastructure at theradio edge of a network, both wired and wireless network interfaces maybe included. When ED 52 is a wirelessly connected device, such as a UserEquipment, radio access network interface 72 may be present and it maybe supplemented by other wireless interfaces such as WiFi networkinterfaces. The network interfaces 58 allow the electronic device 52 tocommunicate with remote entities such as those connected to network 74.

The mass storage 62 may comprise any type of non-transitory storagedevice configured to store data, programs, and other information and tomake the data, programs, and other information accessible via the bus60. The mass storage 62 may comprise, for example, one or more of asolid state drive, hard disk drive, a magnetic disk drive, or an opticaldisk drive. In some embodiments, mass storage 62 may be remote to theelectronic device 52 and accessible through use of a network interfacesuch as interface 58. In the illustrated embodiment, mass storage 62 isdistinct from memory 56 where it is included, and may generally performstorage tasks compatible with higher latency, but may generally providelesser or no volatility. In some embodiments, mass storage 62 may beintegrated with a heterogeneous memory 56.

The optional video adapter 64 and the I/O interface 68 (shown in dashedlines) provide interfaces to couple the electronic device 52 to externalinput and output devices. Examples of input and output devices include adisplay 66 coupled to the video adapter 64 and an I/O device 70 such asa touch-screen coupled to the I/O interface 68. Other devices may becoupled to the electronic device 52, and additional or fewer interfacesmay be utilized. For example, a serial interface such as UniversalSerial Bus (USB) (not shown) may be used to provide an interface for anexternal device. Those skilled in the art will appreciate that inembodiments in which ED 52 is part of a data center, I/O interface 68and Video Adapter 64 may be virtualized and provided through networkinterface 58.

In some embodiments, electronic device 52 may be a standalone device,while in other embodiments electronic device 52 may be resident within adata center. A data center, as will be understood in the art, is acollection of computing resources (typically in the form of servers)that can be used as a collective computing and storage resource. Withina data center, a plurality of servers can be connected together toprovide a computing resource pool upon which virtualized entities can beinstantiated. Data centers can be interconnected with each other to formnetworks consisting of pools computing and storage resources connectedto each by connectivity resources. The connectivity resources may takethe form of physical connections such as Ethernet or opticalcommunications links, and in some instances may include wirelesscommunication channels as well. If two different data centers areconnected by a plurality of different communication channels, the linkscan be combined together using any of a number of techniques includingthe formation of link aggregation groups (LAGs). It should be understoodthat any or all of the computing, storage and connectivity resources(along with other resources within the network) can be divided betweendifferent sub-networks, in some cases in the form of a resource slice.If the resources across a number of connected data centers or othercollection of nodes are sliced, different network slices can be created.

In embodiments, systems and methods are provided for customizing avirtual network that include: 1) Learning available infrastructurenetwork topology and determining an available infrastructure network;and, 2) Designing one or more service-based slice/virtual networks foreach types of service to be supported. The embodiments may include, forinstance, designing and configuring the infrastructure network topologyand Transmission (Tx)/Receiving (Rx) scheduling requirements of eachcommunication party requiring access to the service (network nodes,electronic devices (fixed and/or mobile) onto the infrastructure networknodes and electronic devices. In some embodiments, the customizing maybe performed once and then the virtual network is operated as a fixedcustomized network. In some embodiments, the customizing may beperformed dynamically and then the virtual network is operated as adynamically customized network that allocates and modifies resourcesduring operation to match network performance to current servicerequirements for that virtual network. Learning may pertain toautomatically obtaining information about a subject (e.g. availableinfrastructure network topology) and processing the obtained informationinto further information indicative of the subject. Designing maypertain to automatically generating output indicative of an object (e.g.a network slice or virtual network), the output usable to configurenetwork resources to provide the object.

In some embodiments, the systems and methods enable optimized networkdeployment, operation and maintenance of networks, and enables fullautomation of deployment, operation, and maintenance of virtual networkson an underlying infrastructure network topology.

FIG. 2 is a flow chart illustrating an embodiment of a customizingmethod 900 for customizing a communication network. Available input forthe customizing method 900 may include, for instance, available inputparameters such as: layout of communication components (physical layoutMAP which includes (initial) gNB/AP sites, i.e., locations of networknodes, factory devices with communication modules, or moving path ofmobile devices, etc); characteristics of available communicationcomponents; communication/service level topology (service levelcommunication topology); and service traffic patterns (if available) forthe requested service.

In learning step 905, the available physical infrastructure networktopology is evaluated. The available infrastructure network topology mayinclude defined network nodes that are pre-defined or specified, networkdetected nodes which may be dynamically detected by a network function,or a combination thereof. The network nodes may include, for instance,fixed devices, such as network servers, network EDs, radio access nodes,fixed access nodes, and stationary EDs, as well as mobile devices whichmay provide network support or are end use devices seeking access to thecommunication network. The evaluation of available infrastructurenetwork topology may involve learning through observing and recordingwireless communication operations, as will be explained elsewhereherein.

In slice customization step 910, a service slice (e.g. a virtualnetwork) may be defined for one or more required services based on aservice-level communication/service topology in combination with Qualityof Service (QoS)/Quality of Experience (QoE) requirements, known orpredicted traffic patterns, etc. In general, the slice customizationstep 910 involves defining service requirements for the slice anddefining user plane parameters required to achieve the defined servicerequirements. This can be performed using a slice customizationfunction. In the example of FIG. 2, three separate services have beencustomized. Service 1 supports fixed EDs (e.g. fixed UEs) with knowntraffic patterns by defining user plane parameters for Service 1. Anexample of Service 1 would be for fixed utility meters that are able tocommunicate at scheduled times, such as off hours, to minimize costwhile maintaining connectivity on a regulated schedule. Service 2supports fixed EDs with known traffic statistics patterns by defininguser plane parameters for Service 2. An example of Service 2 would befor a business customer that had predictable but non-scheduledconnectivity requirements. The predictable requirements may be generallyconsistent so as to allow for statistical analysis and prediction ofdata traffic and connectivity requirements. Service 3 supports mobileEDs with known traffic patterns, such as a postal service with mobiledelivery units. The mobile units may require connectivity during eachshift which while servicing their pre-determined delivery routes. Otherexamples may include mobile units with known traffic statisticsinformation, fixed units with unknown traffic information and mobileunits which, while individually having an unknown traffic pattern withina geographic region, may in aggregate have either a known orstatistically predicted traffic pattern within a defined region.

In infrastructure customization step 915, aslice-aware/service-customized infrastructure network topology isdefined based on a service-customized slice as defined in step 910 andbased on an available infrastructure network topology learned in step905. This operation can be performed by an infrastructure networkcustomization function.

In optional monitoring step 920, the defined network may be optimized byreturning to step 905 and learning a current physical infrastructurenetwork topology and repeating steps 905, 910, and 915 to maintain anoptimized virtual network.

In various embodiments, this solution is a further extension of a MyNETsolution. The MyNET solution provides an example of a system and methodfor the entire network architecture and creation/adaptation of servicecustomized slice (virtual network). The additional functionalitiesrequired for the proposed customizing method 900 may include, forinstance: Infrastructure network learning controller; Infrastructurenetwork learning controller to control the learning procedure 905, forinstance through SONAC-COM (MyNET function) which supports some or allof customization of slices/virtual network, a QoS for each device link,such as, D-D link, Uu link could be defined, and the multi-linktransmission for reliability for each Uu and side-link of each device;Customization of the infrastructure network—MyNET, an InfM function withextended capability for defining of physical operation parameters; CM(MyNET CM function) providing for mobile UE connection management andaMAP management; CSM (customer service management) (MyNET CSM function)providing slice access control (AAA), performance assurance of a virtual(slice) performance, including the ability to detect/receive statisticsof SL/Uu link failure rate and other relevant information; and, DAM(data log and analysis) (MyNET DAM function) that may provide data logand analytics to other functionalities. SONAC refers to Service-OrientedNetwork Auto Creation function, which may have network slice composition(SONAC-COM) and network slice operation (SONAC-OP) components. MyNET isdescribed in detail in the paper “Future Wireless Network: MyNETPlatform and End-to-End Network Slicing,” by H. Zhang, submittedNovember 2016 and available at arxiv.org. D-D link refers to a linkbetween devices. Uu link refers to a communication link between a mobiledevice and the network. The side-link (also referred to as “SL”) is adirect peer-to-peer or device-to-device link for example betweenin-vehicle communication systems. The term “aMAP” refers to an accessmap for providing geographic details of radio access.

In more detail, an infrastructure network learning controller maycontrol the learning procedure. An infrastructure management (InfM)function may be used to customize the infrastructure network. Aconnection management (CM) function may provide for mobile UE connectionmanagement. An Authorization, Authentication and Accounting (AAA)function may provide access control functionality. A data analyticsmanagement (DAM) function may perform data logging and data analytics,to support other functions.

In an embodiment, a method is provided for identifying an availableinfrastructure network topology based on the plurality of network nodesand network links of a communication network. The availableinfrastructure network topology consists of a set of available networklinks and a set of available network nodes of the communication networkwhich are to be determined by a learning function operative on at leastone of the network nodes of the communication network. In suchembodiments, the network node transmits a learning schedule to aplurality of network nodes interconnected by a set of network links ofthe communication network. The learning schedule directs each of theplurality of network nodes to perform network performance observationsas observed by that network node. The plurality of network nodes eachperform the network performance observations directed by the learningschedule and transmit back to the learning function a communication noderecord indicative of the network performance observations observed bythat network node. The learning function evaluatesthe communication noderecords to identify available network links from the set of networklinks that meet a pre-determined performance requirement (such as a SNRthreshold for that network link). The available network links furtheridentifies a set of available network nodes that correspond to the setof available network links.

The network performance observations can include data derived based onreception of test messages or other messages communicated to a node. Forexample, the network performance observations can include whether amessage was received, that the signal strength, error rate, etc. was forthe message, other physical characteristics of the message, etc. Thenetwork performance observations can indicate signal reliability,tolerance to interference, levels of interference, etc.

In more detail, the performance requirement for a link indicates whatlevel of performance of a communication link is required for satisfyingspecific purposes of a specific node or set of nodes served by thatlink. The link can serve nodes directly coupled to the link as well asnodes which communicate via multiple links including the link. Theperformance requirement can include that the link supports a given datarate, a given SNR, a given reliability, a given set of modulation andcoding schemes, a given set of frequencies, etc., or a combinationthereof.

Referring to FIG. 3, in an embodiment for fixed EDs, the 5G-definednetwork entry procedure and system information may be used to broadcastan “available infrastructure network topology learning schedule” 1000,and an “observation reporting schedule”. The observation reportingschedule indicates when communication nodes/devices are to reportobserved communication node records.

The learning schedule 1000 includes an identifier 1002 of the nodes ordevices to which the schedule pertains, as well as entries 1004 for aplurality of time indexes 1006. The time indexes can be identified byframe number, for example. For each entry, transmission activities 1008to be monitored and reception activities 1010 to be monitored at thecorresponding time index are identified. Monitoring activities maycomprise logging particular parameters for those activities.Transmission activity parameters may include the UU link or side link IDused, the transmission power used, the transmit code or encoding typeused, and the transmission beam or beam type used. Reception activityparameters may include the UU link or side link ID used, the code orencoding type used at the receiver, and the beam or beam type used atthe receiver.

The logged activity parameters may be reported to the infrastructurenetwork learning function. The infrastructure network learning functionmay process this information to determine links, and characteristicsthereof (e.g. SNR or QoS parameters, best channels, modulation andcoding schemes, or beamforming schemes, or a combination thereof), inthe available infrastructure network topology.

In an embodiment illustrated in FIG. 4, a set of communicationnodes/devices of a communication network may each perform a method forreporting a communication node record indicative of the availablecommunication elements contactable by that network node. In step 1105,based on the learning schedule, the communication nodes/devices performthe operation of transmission and receiving, using the indicatedoperation parameters to observe a communication node record. Thecommunication node record may include, for instance, a number of Txrepeating, code, power level(s), beams, Tx strength, Rx strength, etc.The communication record may include details of communication operationsperformed by the communication nodes/devices, such as what transmissionpower, code rate, number of transmission repeats, transmit or receivebeam configuration, etc. was used by a particular node at a particulartime. Observing the communication node record may correspond toobserving the details of communication operations carried out by a nodeor device.

Based on the observed communication node record, in step 1110 thenodes/devices record the communication record including, for instance,Record i: Time (frame #), beam index, SNR, time offset relative to areference, etc. and any other relevant parameters. The communicationrecord may be recorded in memory and stored at least until reported.

Based on the reporting schedule, in step 1115 the communicationnodes/devices each perform a reporting operation to report the observedcommunication record in the form of an observation report message thatmay include, for instance, a communication node/device ID and a list ofrecords observed by that node/device. The node/device may transmit theobservation report message to a network learning controller available onthe network using an ‘observation reporting schedule’ defined resource.Multiple records may be sent together in the same report message. Theobservation reporting schedule may specify when the reports are to besent and other details such as what node the reports are to be sent toand what information the reports are to include.

In an embodiment illustrated in FIG. 5, a network learning controllermay perform a method for learning an available infrastructure networktopology based on pre-configured acceptable signal-to-noise ratio (SNR)criteria and the received communication node records for each reportingnode. The learning method may enable a customized infrastructure networkoperative to optimize the interference management and maximize theresource utilization and minimize the cost of infrastructure networkdevelopment. Learning the available infrastructure network topologybased on SNR criteria may involve determining, based on communicationnode records or other reported information, what links are present inthe available infrastructure network topology which satisfy apredetermined SNR requirement. For example, if all links require atleast an SNR level greater than a first threshold, the availableinfrastructure network will be determined such that it only includeslinks exhibiting an SNR above this first threshold. SNR requirements canadditionally or alternatively be specified on a link-by-link basis.

According to various embodiments, learning of the availableinfrastructure network topology is performed on an ongoing basis, orperiodically, or in response to an automatic or manual trigger. Invarious embodiments, the available infrastructure network topology isdetermined based on a plurality of observations taken over a range oftimes. Statistical processing can be performed on the plurality ofobservations. The statistical processing can provide statisticallygenerated indications of network conditions such as link SNR values. Thestatistical processing can be performed so as to filter out random andshort (e.g. instant) fast fading events on available links. Thismitigates the probability that the available infrastructure networktopology could be determined based on intermittent fading events that donot accurately reflect long-term network conditions.

In some embodiments, the plurality of observations taken over the rangeof times can be input into an adaptive filter. The adaptive filter maybe configured to filter out random and instant fast fading events. Theadaptive filter may further be configured to provide indications ofnetwork conditions (e.g. link SNR values) such that the adaptive filteris responsive, with adequate speed, to long-term changes in networkconditions and also such that the adaptive filter is robust toshort-term events such as fast fading events. In some embodiments, othersmoothing or averaging mechanisms can be used to filter out intermittentevents such as fast fading events. For example, a moving average can betaken of observations such as link SNR observations over a period oftime, and the moving average can be output as the observation upon whicha determination of the available infrastructure network topology ismade.

An available infrastructure network topology includes a set of networklinks each connecting at least one pair of transmitting (Tx) andreceiving (Rx) nodes. The following network link information may be usedto describe each network link: link ID; sending node/device ID, Txparameters during learning phase; Receiving node/device ID, Rx parameterused during learning phase; SNR; and a Timing offset. The Tx parametersmay be parameters used during the learning phase.

In step 1205 the network learning controller identifies, ranks, or sortsthe reporting nodes based on Tx strength. In step 1210 the networklearning controller calculates a potential link SNR for a correspondingnetwork link between each Rx node relative to a corresponding Tx nodefor that link, with or without interference of other nodes as may bepreferred. In step 1215, if the calculated potential SNR is higher thana pre-determined threshold SNR, then the link between the Tx node andthe receiving node is marked as an available link for the availableinfrastructure network topology. After completing the learning methodfor all communication nodes, and corresponding network links, theavailable infrastructure network topology may be determined as acollection of all available links that meet the pre-determined SNRthreshold. The learning method may be performed as part of an initiallearning procedure to establish the available infrastructure networktopology. In some embodiments, the learning method may be performedperiodically to update the available infrastructure network topologyaccording to an update schedule. In some embodiments, the learningmethod may be performed on-demand to update the available infrastructurenetwork topology as needed based on current requirements, QoS/QoEmeasurements for the corresponding network slice, or other networkmanagement requirements.

In embodiments where mobile nodes/devices are a part of the network,additional positional information may be required. In these embodiments,control and learning for fixed nodes is performed as described above. Amobile learning schedule may be provided for testing mobile nodes. Thelearning schedule may include, for instance, positioning information,timing information, and signal strength information.

In an embodiment where GPS or 3GPP positioning information is available,the mobile learning schedule for a mobile node may include a receivedTx/Rx schedule which may include Tx information such as a locationindex, time, power, beam, code, etc, and Rx information such as locationindex, time, beam, code, etc.

In an embodiment where GPS or 3GPP positioning information is notavailable, the mobile learning schedule for a mobile node may include areceived Tx/Rx schedule which may include Tx information such as time,power, beam, code, etc., and Rx information such as time, beam, code,etc.

The learning at a mobile node that is being tested may include, Tx/Rxbased on schedule; a mobile node observation record that may include alocation index, time, code, SNR/signalling strength, time offset, etc.;and, observation record reporting that may include, for instance, a listincluding all mobile node observation records for that node, transmittedto the learning controller using network resources defined in an‘observation reporting schedule.’

The learning controller is operative to receive the observation recordsprovided by the mobile nodes, and with DAM support, determine apotential network link SNR for each location and time. The learningcontroller may then use the method of FIG. 5 to determine whichcommunication nodes will support mobile connectivity.

The available network links for mobile nodes may be included in thedefinition of an available infrastructure network topology. In someembodiments mobile link ID's may include, for instance, a link ID; asending node/device or location (e.g., cubic ID) and Tx parameters usedduring learning phase; a receiving node/device or location (e.g., cubicID) and Rx parameters used during learning phase; SNR; and, a timingoffset.

In an embodiment, network slices (virtual networks) may be customizedbased on the service level topology and service description, provided bya network customer, such as a utility provider, business, government,etc. A defined customized network slice may include: Virtual function(s)in available network nodes and devices and a logical topology amongthese nodes and devices and other virtual network functions; Physicallinks (capacity requirement, latency requirement) for each logical linkwhere available (e.g., for fixed devices, the side link and Uu link);Transmission type—Broadcast/multicast/unicast type; L2/3 protocols foreach of these logical links and physical links.

In embodiments an infrastructure network topology may be customized. Forinstance, for MyNET design a network slice is first created based on aslice definition. The slice definition includes infrastructure networkresource allocation for the network slice, i.e., a group of devices.This may be performed by SONAC-COM. During the operation of such aslice, the slice resources need to be further real-time allocated toeach of the devices, on an on-demand basis. This may be performed bySONAC-Op. Given the characteristics of vertical services, i.e., known orplannable traffic patterns and or known or plannable devices mobilitypattern, the slice resource allocation can be pre-defined/configured,and the Tx/Rx/power-off of each node/device (fixed or mobile) can beoptimally designed to minimize interference.

For services with predictable traffic patterns and fixed devices, theinfrastructure network customization manager, based on the availableinfrastructure network topology from Learning controller and slicedesign from SONAC-COM, determines, for each communication node/device afixed infrastructure resource allocation that includes a Tx timeschedule table and a Rx time schedule table. The manager ofcustomization of infrastructure network (infrastructure networkcustomization manager) can be an infrastructure network customizationfunction.

The Tx time schedule table may include, for each of the Tx opportunitiesin Un and SL: broadcast/multicast/unicast; and, for each timeopportunity (e.g., frame number(s), etc): Carrier(s)/frequency(s); Beamindex(es); DM-RS/Code(s); Tx power; MCS; Time advance; etc. DM-RS refersto a demodulation reference signal.

The Rx time schedule table may include, for each time opportunity (e.g.,frame number(s), etc) (in Uu or SL): Carrier(s)/frequency(s); Beamindex(es); DM-RS/Code(s); MCS; etc. MCS refers to modulation and codingscheme.

For services with unpredictable traffic pattern, unpredictable mobilepathing of devices, or both, the manager of infrastructure networkcustomization, based on the available infrastructure network topologydetermined by the learning controller and slice design from SONAC-Com,determines, for each fixed communication node/device and each of itslinks (Un/SL), Tx resource allocation windows (a set of basic physicallayer resources, over time), and a Rx time schedule table.

For each Tx window the manager determines whether a Tx request is neededor not. If needed, the manager sends a request for each Tx of traffic.For each time opportunity (e.g., frame number(s), etc), some or all ofthe following could be included: Carrier(s)/frequency(s); Beamindex(es); DM-RS/Code(s); Tx power; MCS; Time advance; etc.

The Rx time schedule table may include, for each time opportunity (e.g.,frame number(s), etc) in Uu/SL, some or all of the following:Carrier(s)/frequency(s); Beam index(es); DM-RS/Code(s); MCS; etc.

The manager of infrastructure network customization further determines,for each of the mobile devices, location-based resource assignments if aMAP is available. In this situation a Tx/Rx schedule table may include aTx (Uu/SL) for each location index and a Rx (Uu/SL) for each locationindex.

The Tx (Uu/SL) may include, for each location index: Time window; Power;Carrier/frequency; DM-RS/Codes; Beam index (antenna configuration); etc.

The Rx (Uu/SL) may include, for each location index: Time window;Carrier/frequency; DM-RS/Codes; Beam index (antenna configuration); etc.

If traffic patterns and mobility pathing are not available orpredictable, the corresponding network slice definition may include aset/block of resources (e.g., a set of basic physical layer resourceunits) in Uu and SL for at least some of the nodes/devices. A real-timescheduler function may be implemented in the corresponding nodes/devicesto allow for real-time resource scheduling.

In an embodiment a service-customized Network Operation SupportingServices (NOS) plane may be provided. In these embodiments, to enablecustomization of the infrastructure network topology the NOS functionsneed to be able to communicate with the devices/nodes of the availableinfrastructure network topology. In order to communicate, infrastructureresources need to be defined and allocated. In order to design such aNOS slice, the service level topology of that slice needs to be defined.

Referring to FIG. 6A, in a first use case example assuming fixednodes/devices and a deterministic (scheduled or predictable) trafficpattern(s) and transmission time(s). In this case network links can berelatively static and a dynamic link scheduler may be convenientlyomitted. The NOS functions for the fixed and deterministic case mayinclude: an infrastructure network learning controller 616; SONAC-COM;customization of infrastructure network; CSM (AAA 622, performanceassurance 626); and DAM 624. The customization of the infrastructurenetwork can be performed by an infrastructure network customizationmanager 614 (also referred to as a manager of infrastructure networkcustomization). A slice customization controller 618 is alsoillustrated, which operates to define customized network slices, forexample based on customer requirements, as described elsewhere herein.

In the first use case example the CSM-AAA 622 is operative to performAAA for each of the fixed nodes/devices 630. The infrastructure networklearning controller 616 is operative to configure each of nodes/deviceto control the learning phase. The infrastructure network customizationmanager 614 is operative to configure the nodes/devices for operation.As illustrated in the embodiment of FIG. 6A, these services areconfigured as a STAR topology.

Further in the first use case example, DAM is configured to collect datafrom communication elements and infrastructure equipment. QoSrequirements are associated with the logical connections. Thecommunication elements include fixed communication elements, such asnetwork nodes and fixed networked devices 630.

FIG. 6B illustrates a variation of FIG. 6A, in which the AAA, DAM and PAfunctions are omitted for clarity, and operational relationships betweenthe infrastructure network learning function 646 (comparable toinfrastructure network learning controller 616), slice customizationfunction 648 (comparable to slice customization controller 616) andinfrastructure network customization function 644 (comparable toinfrastructure network customization manager 614) are shown in moredetail. FIG. 6B is explained in more detail below. FIG. 6A can includesimilar features. Network nodes and fixed devices 630 are alsoillustrated. The fixed devices may be viewed as client devices accessingthe wireless network.

Consider a factory, city, or other environment having a number ofwireless communication devices in fixed locations (mobile devices canalso be considered in other embodiments). The devices can be generallyregarded as network nodes 630, and can include end use devices such asInternet of Things (IoT) devices integrated into machinery or otherenvironmental equipment, as well as management devices and wirelessaccess points or base stations. Once the devices are deployed in anenvironment, it is possible to monitor their wireless transmission andreception operations to determine which devices are capable ofcommunicating with each other, and the parameters (e.g. signal to noiseratios (SNRs)) associated with such communications. This information isreferred to as an available infrastructure network topology and can beconceptualized as a network graph comprising network nodes andcommunication links therebetween with specified characteristics (e.g.SNRs). This process can be managed by the infrastructure networklearning function 646, by directing various devices to performtransmission and reception functions according to a specified availableinfrastructure network topology learning schedule (or simply learningschedule), and to report the results according to a specifiedobservation reporting schedule (or simply reporting schedule).

The learning schedule can be as illustrated in FIG. 3. That is, thelearning schedule can indicate, for each network node, differenttransmission operations, reception operations, or both, to perform atdifferent times. The learning schedule can indicate parameters of thetransmission or reception operations, as well as parameters to berecorded and reported. Nodes can perform the transmission and receptionoperations according to the learning schedule, as well as subsequentrecording and reporting operations, as illustrated for example in FIG.4.

For the purpose of implementing the learning process, the infrastructurenetwork learning function 646 is communicatively coupled (directly orindirectly) to the network nodes 630. In some embodiments, the learningschedule is structured and includes instructions to transmit testmessages at specified times from specified nodes, and to monitor forthose test messages at other specified times at other specified nodes.Different test messages can be transmitted concurrently or sequentially,or a combination thereof. Different test messages can be transmitted atdifferent specified powers, in order to determine which transmit poweris required for an adequate communication link between nodes. In someembodiments, the learning schedule instructs nodes to monitor and reporton communications operations that occur during their normal operation,over a predetermined period of time.

For example, in one embodiment, each node 630 can transmit a testmessage at a specified time and at a specified power, and each othernode can monitor to determine whether this test message can be receivedand decoded. Multiple test messages can be transmitted, with differentphysical parameters. For each successful communication of a test messagebetween a given transmitting node and a given receiving node, theinfrastructure network learning function determines that a link betweenthe given transmitting node and the given receiving node is available,at least for the specified physical parameters used in that testmessage.

In some embodiments, the infrastructure network learning function canoperate as illustrated in FIG. 5, in order to identify network linksbetween transmitting nodes and receiving nodes as available networklinks in the available infrastructure network topology. That is, networklinks can be identified as being available when they have sufficient SNRlevels.

Identifying the available network links is performed based on anevaluation of the communication node records. In particular potential(i.e. candidate) network links are evaluated and deemed to be availablenetwork links if a performance requirement, such as a sufficient SNRlevel, is met for that potential network link.

Based on the determined available infrastructure network topology 652,various customizations can be carried out. The available infrastructurenetwork topology information can be provided to an infrastructurenetwork customization function 644, a slice customization function 648,or both. The slice customization function 648 can also be provided withcustomer requirements 650, such as communication topology requirementsand quality of service (QoS) requirements. For example, the customerrequirements 650 may specify which devices should be directly connectedto each other via communication links, the parameters of communicationlinks required between devices (either directly or indirectlyconnected), etc. The customer requirements 650 may also specify thecommunication characteristics for certain devices (e.g. when and howoften they communicate, the type of information communicated, etc.)Based on the available infrastructure network topology information 652and the customer requirements 650, the slice customization function 648can be configured to specify parameters 654 for one or more serviceslices to be deployed to support the customer. Each service slice is anetwork slice or virtual network having a defined network topology withspecified links, and specified QoS for each link. The service slice maydefine other aspects such as network functions, resource allocations ofequipment, allocations of communication resources to be used, etc.

The parameters 654 specified for the service slices are provided, alongwith the available infrastructure network topology information 652, tothe infrastructure network customization function 644. Theinfrastructure network customization function 644 defines a servicecustomized infrastructure network, having a topology which consists ofnodes and links belonging to (and typically a strict subset of) theavailable infrastructure network topology 652. Furthermore, the servicecustomized infrastructure network includes nodes and links which aresufficient to support the one or more service slices that are to bedeployed. This includes a sufficient number of nodes, and types ofnodes, at required locations, and with required quality of links betweennodes, in order to support the service(s) to be operated using thenetwork slice(s).

The service customized infrastructure network is also defined, by theinfrastructure network customization function 644, to include a specificschedule (link schedule), specifying communication operations betweennetwork nodes. The schedule may be a fixed communication schedule. Thatis, nodes receive, store and operate according to the scheduleindefinitely until it is updated. The schedule can define times at whichspecified nodes communicate with other specified nodes, portions of apool of shared wireless resources (e.g. frequencies, time slots, codes,modulation and coding schemes, or other physical parameters) used forsuch communication, or a combination thereof. The schedule can becommunicated to the nodes and subsequently used thereby. For thispurpose, the infrastructure network customization function iscommunicatively coupled (directly or indirectly) to the network nodes.The network nodes may be provided with configuration instructions,including the instructions to communicate according to the schedule,prior to deployment of the service. The network nodes may additionallybe reconfigured after deployment of the service.

Accordingly, because a service customized infrastructure network isdeployed, the need for a real-time scheduler is mitigated. A real-timescheduler can still be included, in some embodiments, in the case wheremobile nodes are also present in the service customized infrastructurenetwork. When the real-time scheduler is omitted or reduced in its scopeof operations, the network is simplified and more efficient. Theefficiency is achieved in part because scheduling messages are notrequired, or required to a lesser extent. Instead, the nodes areprovided with a schedule a priori. This schedule is referred is referredto as a fixed communication schedule, and nodes are directed tocommunicate according to it, typically for a period of time encompassingmultiple successive communication opportunities. This is possible due tothe predictability of communications operations which in turn is derivedfrom knowing the customer requirements and (through learning) theavailable infrastructure network topology.

FIG. 7 refers to a second use case example assuming a combination offixed EDs 630 and mobile EDs 632 having non-predictable mobile paths andtraffic pattern. In this case network links supporting the mobile EDsare preferably dynamic and, accordingly, a dynamic link scheduler, alsoreferred to as a real-time scheduler 1405, may be conveniently includedto support the AN(s) 1410. In some aspects, the real-time scheduler 1405may comprise a network function instantiated at, or logically close to,the AN 1410. The NOS functions for the mobile and non-predictable casemay include: an infrastructure network learning controller 616;SONAC-COM; customization of infrastructure network (e.g. aninfrastructure network customization manager 614); CSM (AAA 622,performance assurance 626); DAM 624; CM 634; and real-time per-linkscheduler 1405. The real-time scheduler 1405 operates to schedulecommunication with the mobile EDs 632. The slice customizationcontroller 618 is also present.

The mobile EDs 632 may be networked vehicles, autonomous mobile devices,mobile camera or other monitoring equipment, mobile machinery, or mobileuser equipment, etc. During learning of the available infrastructurenetwork topology, test mobile EDs can be made to move through apredetermined area, periodically transmitting test messages according tothe learning schedule, and monitoring for messages transmitted by otherEDs according to the learning schedule. When a mobile ED reportsinformation obtained during learning, it can also report its location atthe time of each observation being reported. The infrastructure networklearning controller 616 (or its corresponding function) can then usethis information to generate scheduling information indicating whichfixed devices (e.g. base stations) should be used to communicate withmobile EDs with given requirements in a given area. This schedulinginformation may be provided to the real-time scheduler 1405 and usedthereby to schedule communications with mobile EDs following thelearning phase. This providing may be performed by the infrastructurenetwork customization manager 614 as part of customization of theinfrastructure network. That is, the real-time scheduler 1405 may becustomized based on information gathered during the learning of theavailable infrastructure network topology. Other aspects of FIG. 7 arethe same as or similar to those of FIGS. 6A and 6B.

In the second use case example, there is a similar service leveltopology as for the first use case example. In this case, CMcommunicates with mobile devices and CM also has a STAR service leveltopology. The real-time scheduler 1405 has a STAR topology with themobile devices.

For vertical/industry customers, all of these functions supporting anetwork slice can share a same NOS slice resource for their individualrequirements. In some embodiments, NOS messages may be differentiatedbetween functions by including a message type field to indicate in eachNOS message which of the functions, such as SONAC-COM, Learning control,DAM, CM, InfM, etc., is affiliated with that NOS message.

Embodiments of the systems and methods described herein provide for theability to integrate control/management functionalities to simplifynetwork deployment/operation/maintenance. The initial learning process,and optionally the ability to perform on-going learning of currentinfrastructure network capabilities, optimal networkdeployment/operation/maintenance becomes possible by effectivelyallocating, and optionally re-allocating, resources to support a networkslice in meeting its service requirements. Unlike current methods, whichrequire either over-allocation to ensure meeting high servicerequirements, or allowing service requirement slippage in times of highdemand, equipment failure, or other inability of allocated resources tomeet current requirements, the embodiments described herein allow foraccurate initial allocation based on specific service requirements, andallows for re-allocation based on current requirements or resourceavailability.

In some embodiments, machine learning or artificial intelligence (AI)may be used to allow for a reactive allocation process that adaptsresource allocation for a network slice in response to changing customerrequirements while meeting an established service policy for thatnetwork slice.

In some embodiments, network robustness may be enabled by identifyingspecific network links that may require higher reliability andallocating alternative links to support dual connections to maintainservice through infrastructure failure affecting one of the links. Insome embodiments, the dynamic learning and re-allocation of networkresources may provide for a self-healing network that is operative toinstantiate backup or alternative links to support service requirementswhile the original link problem is being addressed.

FIGS. 8 to 13 provide illustrative embodiments of use case examples andnetwork infrastructure topologies to better describe the systems andmethods described herein.

Referring to FIG. 8, a use case example is provided for fixednodes/devices with a predictable traffic pattern. Element layout 1505illustrates the various hardware components including components 1509with an application module and a communication module, e.g. networknodes and UEs, and components 1509 that are primarily communicationmodules, e.g. gNB, AP, etc.). The element layout 1505 may be pre-definedfor the learning module, for instance based on a network architecturediagram, or may be constructed by the learning module evaluating thenetwork components. In some aspects the element layout 1505 may bedeveloped by a combination of pre-definition and machine learning.

In the example use case of FIG. 8 it is intended that a verticalcustomer, such as a business or utility, is able to provide an elementlayout 1505 of available network nodes 1507 and EDs 1509 indicatingtheir relative logical locations. After performing the systems andmethods described herein, an available infrastructure network topology1510 may be constructed indicating the available connections 1512between nodes/devices of the network. The available infrastructurenetwork topology includes, in addition to the elements defined in theelement layout 1505, a set of links connecting the elements. Each of thelinks may be associated with a link quality, such as SNR, that wasdetermined during the learning phase. In various embodiments, operationsof FIG. 8 are performed by the infrastructure network learningcontroller 616 (or infrastructure network learning function 646).

In more detail, FIGS. 8 to 10 can be regarded as illustrating an exampleuse case based on FIGS. 6A and 6B, where the network nodes are in fixedlocations. FIGS. 8, 9 and 10 illustrate successive operations carriedout in series, for example following the order of operations shown inFIG. 6B. Some of the network nodes may be base stations while the othersmay be operatively coupled to industrial machines, monitoring equipment,or other end devices. The infrastructure network learning functiondirects the components (i.e. the network nodes 1507 and EDs 1509) toperform the operations described for example in FIG. 4. For clarity, theEDs 1509 can also be considered to be network nodes in a more generalsense. Based on the obtained information, the infrastructure networklearning function determines the available network infrastructuretopology 1510, based for example on operations such as illustrated inFIGS. 5 and 6B. The determined topology 1510 is passed to theinfrastructure network customization function. For each connection 1512(i.e. link), a SNR value is provided. Each SNR value may be specific toits associated link, but all SNR values will generally be higher than athreshold value deemed adequate for communication between endpoints ofthe associated link.

In the example use case of FIG. 9, a customized network slice 1615, orslices, may be determined based on an available infrastructure networktopology 1510 and a service level topology 1610 defined for the serviceto be supported. The service level topology definies QoS/QoErequirements for the network slice, as well as any service/communicationtopologies that need to be defined. In the example use case of FIG. 9,the service level topology of devices in PLC1 group 1620 is a STARtopology, devices in PLC group 2 1622 is a chain topology, and theservice level topology in C-C group 1624 is a mesh topology. Eachconnection/link in these topologies 1620, 1622, 1624 may be associatedwith a set of QoS requirements and optionally a traffic transmissionplan. A service-customized network slice 1615 may be designed based onthe service level topology 1610 and the available infrastructure networktopology 1510. In various embodiments, operations of FIG. 9 areperformed by the slice customization controller 618 (or slicecustomization function 648).

The service level topology may be a logical network topology. Theservice level topology may define a subset of network nodes andcommunication requirements (e.g. QoS requirements) between pairs of thissubset.

The slice 1615 may be defined based on the service level topology, QoSrequirements, traffic plan and available infrastructure network topology1510. The network slice may be designed based on service levelrequirements, service level description, and available infrastructuretopology. The network slice definition may indicate the slice logicaltopology, the logical link capacity, and communication protocols to beused. The slice logical topology is defined according to logical links1617 between nodes.

Referring to the service level topology 1610, C-C group 1624 includesthree nodes logically connected by QoS class 1 or QoS class 2 links.PLC1 group 1620 includes four nodes logically connected by QoS class 3links, and PLC2 group 1622 includes six nodes logically connected by QoSclass 4 links. Referring to the service customized slice 1615, differentnodes are again connected by links belonging to different QoS classes.These connections are such that the specified QoS of the logicalconnections in service level topology 1610 are supported. In particular,a path consisting of QoS class 1 links 1617 a is defined in order tosupport the QoS class 1 logical connections between members of C-C group1624, and a path consisting of QoS class 2 links 1617 b is defined inorder to support the QoS class 1 logical connections between members ofthe C-C group 1624. The remainder of the links in PLC1 group 1620 areQoS class 3 links and the remainder of the links in PLC2 group 1622 areQoS class 4 links. The physical link topology of the service customizedslice 1615 supports the logical link topology of the service leveltopology 1610. For example, whereas the service level topology 1610defines QoS class 1 and class 2 logical links directly between differentnetwork nodes, the service customized slice defines QoS class 1 andclass 2 paths which link these network nodes indirectly, viaintermediate nodes and multiple hops.

At least the topology of the customized network slice (i.e. thecustomized network slice topology) is determined based on the availableinfrastructure network topology and the service level topology. Otheraspects of the network slice, such as the proportions of resourcesallocated thereto, may also be determined. The service level topology1610 can be specified by a customer subscribing to the service. Arrows(e.g. between nodes in the service level topology 1610 and slicedefinition 1615, as well as in other figures) denote the direction ofdata flow in communications between nodes. This can be based onspecifications by the customer as part of the service level topology1610. In particular, the customized network slice topology may specifynetwork nodes and interconnections therebetween, where the nodes andinterconnections are a subset of the available infrastructure networktopology. The customized network slice topology can include nodes, andlink qualities, are adequate for delivering a service according to theservice level topology. The customized network slice topology can be alogical network topology.

In the example use case of FIG. 10, a customized infrastructure network1715 may be determined based on an available infrastructure networktopology 1510 and a designed service-customized slice 1615. Given thedesigned service-customized slice 1615, an infrastructure networkcustomization manager is operative to determine which links of theavailable links will be allocated to the customized infrastructurenetwork 1715. For each allocated node/device corresponding to theallocated links, the controller (e.g. the infrastructure networkcustomization manager) defines the per link connection parameters, suchas Tx/Rx schedule, Tx/Rx physical layer parameters, and Rx parameters.Finally, the infrastructure network customization manager configureseach of the allocated nodes/devices based on the defined per linkconnection parameters corresponding to that node/device. The end resultis a service-customized infrastructure network 1715 allocated andconfigured to support the service-customized slice 1615 from theavailable infrastructure network topology 1510. The customizedinfrastructure network may define, for each link 1717 or communicationnode or ED 1719, physical communication parameters (e.g. linktransmit/receive schedules, L1 parameters, transmit/receive beam usage,transmit/receive times, transmit/receive radiofrequency assignments,transmit code usage, time alignments, transmit/receive schedules, etc.).In various embodiments, operations of FIG. 10 are performed by theinfrastructure network customization manager 614 (or infrastructurenetwork customization function 644).

In the example use case of FIG. 11, learning for a combined fixed andmobile layout is illustrated. The element layout 1810 includes fixedcomponents 1507, 1509, as well as one or more test mobile components1812. The test mobile component 1812 may preferably be moved through apre-defined moving path covering all available mobile paths, such asroads, that are intended to be covered by the network. In the exampleillustrated, the test mobile component 1812 is operative to traversealong the available mobile paths, indicated in grey paths. During thelearning phase, a test mobile component 1812, based on a predefinedmoving path, traverses across the available paths. At the same time,based on a predefined Tx/Rx schedule table, the test mobile component1812 may transmit pilot tones and receive signals from othernodes/devices 1507, 1509 available in the network. After the learningphase, the learning controller will create a coverage map 1815, wherefor each cubic (or bin), available links with SNR are identified. FIG.11 illustrates the same layout of fixed nodes/devices 1507, 1509 asFIGS. 8 to 10, and these fixed nodes/devices can be interconnected asshown in those figures. The available links indicate thenode(s)/device(s) 1507, 1509 which a mobile component can connect withfrom a given location. The locations are binned together intorectangular areas for simplicity. SNR values for each available link aredetermined and associated with that link. In various embodiments,operations of FIG. 11 are performed by the infrastructure networklearning controller 616 (or infrastructure network learning function).

In more detail, the test mobile component can inform the infrastructurenetwork learning function of its locations as they are reached oraccording to a planned schedule, or the infrastructure network learningfunction can control the location of the test mobile component. Then, ata plurality of locations, the test mobile component can monitor for testmessages, transmit test messages, or both. The test messages can betransmitted according to a learning schedule directed by theinfrastructure network learning function, for example as illustrated inFIGS. 3 and 4. By processing the reported results of the test messagingfor multiple locations of the test mobile component, for example asillustrated in FIG. 5, the infrastructure network learning controllercan generate the coverage map 1815. The coverage map indicates, for eachlocation area (bin), the stationary node/device that a mobile device inthat location area should communicate with, as well as the SNR for thelink with that stationary node/device.

In the example use case of FIG. 12, given a service level topology 1905,a STAR topology in this example including QoS requirements for eachlogical connection, and available infrastructure network topology 1510and coverage map 1815, a slice designer may design a service-customizednetwork slice 1920 that defines the allocated links and their associatedQoS requirements. The service-customized network slice 1920 can beautomatically designed. The service-customized network slice 1920utilizes backhaul links between nodes 1507, 1509, which correspond toless than all of the available backhaul links defined in the availableinfrastructure network topology 1510 (defined for example as shown inFIGS. 8 to 10). Some of the links are not utilized. Theservice-customized network slice 1920 utilizes radio access linksdefined according to the coverage map 1815. These links are determinedso that they exhibit adequate SNR for supporting a required servicelevel. In various embodiments, operations of FIG. 12 are performed bythe slice customization controller 618 (or slice customizationfunction).

The service level topology 1905 can be specified by the customer,similarly to the service level topology 1610. As shown, the servicelevel topology specifies logical connections of multiple mobile deviceswith a central controller in a star configuration. However, otherconfigurations of logical connections can also be specified. Eachlogical connection is associated with a specified QoS level or classrequirement. The service-customized network slice is designed to meetthese QoS requirements, for example by allocating links with sufficientSNR, bandwidth, etc.

In the example use case of FIG. 13, a customized infrastructure network2010 may be allocated and configured based on a service-customizednetwork slice 1920 and the available infrastructure network topology1510. The customized infrastructure network 2010 includes a set ofallocated nodes/devices and, for each of the allocated linkscorresponding to the allocated nodes/devices, defined Tx/Rx schedule andlink parameters. The final step is configuring each of the allocatednodes/devices based on the defined Tx/Rx schedule and link parameters.For mobile devices, a location-dependent Tx/Rx schedule and linkparameters are defined and configured for each mobile device. In someaspects, the mobile device may only be configured with a sub-set of thelocation-dependent Tx/Rx schedule and link parameters. The network isoperative to configure a further sub-set of location-dependent Tx/Rxschedule and link parameters based on a current location of each mobiledevice. In some aspects, each mobile device may only be configured witha sub-set of location-dependent Tx/Rx schedule and link parameters. Invarious embodiments, operations of FIG. 12 are performed by theinfrastructure network customization manager 614 (or infrastructurenetwork customization function).

In the present example, the customized infrastructure network 2010 hasthe same set of network nodes, network links, and mobile device servicecoverage areas as is defined in the service-customized network slice1920. However, the customized infrastructure network additionallydefines link parameters and transmission/reception schedulinginformation for the network. Additionally, in some embodiments, if thecustomized infrastructure network is designed to support multiplenetwork slices (e.g. different service-customized network slices definedaccording to the preceding discussion), then the network topology may beconfigured so as to support all such slices.

Although the present invention has been described with reference tospecific features and embodiments thereof, it is evident that variousmodifications and combinations can be made thereto without departingfrom the invention. The specification and drawings are, accordingly, tobe regarded simply as an illustration of the invention as defined by theappended claims, and are contemplated to cover any and allmodifications, variations, combinations or equivalents that fall withinthe scope of the present invention.

We claim:
 1. A method for identifying an available infrastructurenetwork topology consisting of a set of available network links and aset of available network nodes of a communication network, the methodcomprising an infrastructure network learning controller of thecommunication network: transmitting a learning schedule to a pluralityof network nodes interconnected by a set of network links of thecommunication network, the learning schedule directing the plurality ofnetwork nodes to perform specified communication operations and recordnetwork performance observations based on said communication operations;receiving, from each node of the plurality of network nodes, arespective communication node record including the network performanceobservations observed by said node based on the learning scheduletransmitted to said node; and providing an identification of the set ofavailable network links from the set of network links based on thereceived communication node records, and providing an identification ofthe set of available network nodes corresponding to the set of availablenetwork links.
 2. The method of claim 1, wherein identifying the set ofavailable network links comprises evaluating communication node recordscorresponding to each potential network link, and including thepotential network link in the set of available network links if thecommunication node records indicate that the potential network linkmeets a predetermined performance requirement.
 3. The method of claim 2,wherein the pre-determined performance requirement comprisescommunication using the potential network link meeting at least aspecified signal-to-noise ratio (SNR) threshold.
 4. The method of claim1, wherein the learning schedule further includes an update schedule foreach node of the plurality of network nodes to transmit communicationnode records to the communication node, and wherein the method furthercomprises: receiving, from each node of the plurality of network nodes,the communication record for said node according to the correspondingupdate schedule.
 5. The method of claim 1 further comprising a slicecustomization controller operatively coupled to the infrastructurenetwork learning controller: determining a customized network slicetopology based on a customer-defined service level topology and theavailable infrastructure network topology, the service level topologydefining a subset of the plurality of network nodes and communicationrequirements therebetween, the customized network slice topologyspecifying network nodes and interconnections from the availableinfrastructure network topology which are adequate for delivering aservice according to the service level topology.
 6. The method of claim5 further comprising an infrastructure network customization manageroperatively coupled to the infrastructure network learning controllerand the slice customization controller: prior to deployment of theservice, configuring a subset of nodes belonging to the set of availablenetwork nodes based on the determined customized network slice topology,said configuring comprising directing the subset of nodes to communicateaccording to a fixed resource allocation including a fixed communicationschedule.
 7. The method of claim 6 further comprising the infrastructurenetwork learning controller: receiving, from at least one node of theplurality of network nodes, at least one further communication noderecord including network performance observations observed by said atleast one node after the subset of nodes has been configured; and,evaluating the set of network links based on the at least one furthercommunication record.
 8. The method of claim 7, wherein the at least onefurther communication node record is received based the learningschedule.
 9. The method of claim 7, wherein the at least one furthercommunication node record is received based on a request previouslytransmitted by the infrastructure network learning controller to theplurality of network nodes.
 10. The method of claim 6 further comprisingthe infrastructure network learning controller: changing at least one ofthe set of available network links or the determined customized networkslice topology based on the at least one further communication record.11. A system comprising an infrastructure network learning controllerfor identifying an available infrastructure network topology consistingof a set of available network links and a set of available network nodesof the communication network, wherein the infrastructure networklearning controller is configured to: transmit a learning schedule to aplurality of network nodes interconnected by a set of network links ofthe communication network, the learning schedule directing the pluralityof network nodes to perform specified communication operations andrecord network performance observations based on said communicationoperations; receive, from each node of the plurality of network nodes, arespective communication node record including the network performanceobservations observed by said node based on the learning scheduletransmitted to said node; provide an identification of the set ofavailable network links from the set of network links based on thereceived communication node records; and provide an identification ofthe set of available network nodes corresponding to the set of availablenetwork links.
 12. The system of claim 11, wherein identifying the setof available network links comprises evaluating communication noderecords corresponding to each potential network link, and including thepotential network link in the set of available network links if thecommunication node records indicate that the potential network linkmeets a predetermined performance requirement.
 13. The system of claim12, wherein the pre-determined performance requirement comprisescommunication using the potential network link meeting at least aspecified signal-to-noise ratio (SNR) threshold.
 14. The system of claim11, wherein the learning schedule further includes an update schedulefor each node of the plurality of network nodes to transmitcommunication node records to the communication node, and wherein theinfrastructure network learning controller is further configured to:receive, from each node of the plurality of network nodes, thecommunication record for said node according to the corresponding updateschedule.
 15. The system of claim 11, further comprising a slicecustomization controller coupled to the infrastructure network learningcontroller, wherein the slice customization controller is configured to:determine a customized network slice topology based on a customer-defiedservice level topology and the available infrastructure networktopology, the service level topology defining a subset of the pluralityof network nodes and communication requirements therebetween, thecustomized network slice topology specifying network nodes andinterconnections from the available infrastructure network topologywhich are adequate for delivering a service according to the servicelevel topology.
 16. The system of claim 15, further comprising aninfrastructure network customization manager coupled to theinfrastructure network learning controller and the slice customizationcontroller, wherein the infrastructure network customization manager isconfigured to: prior to deployment of the service, configure a subset ofnodes belonging to the set of available network nodes based on thedetermined customized network slice topology, said configuringcomprising directing the subset of nodes to communicate according to afixed resource allocation including a fixed communication schedule. 17.The system of claim 16, wherein the infrastructure network learningcontroller is further configured to: receive from at least one node ofthe plurality of network nodes at least one further communication noderecord including network performance observations observed by said atleast one node after the subset of nodes has been configured; andevaluate the set of network links based on the at least one furthercommunication record.
 18. The system of claim 17, wherein the at leastone further communication node record is received based the learningschedule.
 19. The system of claim 17, wherein the at least one furthercommunication node record is received based on a request previouslytransmitted by the infrastructure network learning controller to theplurality of network nodes.
 20. The system of claim 16, wherein theinfrastructure network learning controller is further configured to:change at least one of the set of available network links or thedetermined customized network slice topology based on the at least onefurther communication record.